Assigning to a Call a Unique Key Associated with Caller Specific Data for Retrieving Data From a Database

ABSTRACT

Caller specific information is linked to a call using a key for database retrieval of caller specific data. A pool of rolling Automatic Number Identification (ANI) codes is maintained. A call is received at a rolling ANI device. A rolling ANI is assigned to the call. The assigned rolling ANI is provided in a field identifying the call. The call and the assigned rolling ANI in the field identifying the call is routed to a call handler. A voice path and data associated with the call is received at the call handler. The data is parsed to determine a rolling ANI associated with the call. Caller specific information is obtained from a database record in a database identified by the rolling ANI. The obtained caller specific information is used to process the call seamlessly without prompting the caller for information in the database record associated with the rolling ANI.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a divisional application of U.S. patentapplication Ser. No. 13/831,700 filed Mar. 15, 2013, and titled“Assigning to a Call a Unique Key Associated with Caller Specific Datafor Retrieving Data from a Database,” which is a continuation-in-partapplication of U.S. patent application Ser. No. 13/314,221 filed Dec. 8,2011, and titled “Assigning to a Call a Unique Key Associated withCaller Specific Data for Retrieving Data from a Database,” thedisclosures of which are expressly incorporated herein, in theirentirety, by reference.

FIELD OF THE INVENTION

This disclosure relates in general to a contact center computertelephony integration system, and more particularly to assigning aunique key associated with the caller specific data to each call fordatabase retrieval.

BACKGROUND

A core call center is often used to receive incoming calls. These callsmay then be moved to out-sourced parties or other parties to handle thecalls. More specifically, an automated, interactive voice response (IVR)system receives calls. The voice path and the data must be movedseamlessly to the third party that actually handles the call. Data mayinclude customer account number, customer location information includingcustomer site identifier, and service level information (i.e. types ofservices available in a calling area, services a caller uses,customer-specific information, etc.). Providing all thecustomer-specific data that is relevant to the call to the partieshandling the calls enables a successful transfer of the data and thevoice path. Accordingly, the customer can be handled efficiently andaccurately, with no time wasted asking questions and looking up datathat is previously known about that caller.

The voice path is forwarded with a key in a field, such as the CallingLine Identification (CLI) field. A mechanism is provided for countingcalls and then sending a modified CLI with the call. Thus when a callarrives, a voice path and a key are provided to indicate that the dataassociated with the call may be found using a key to look up adesignated record in a database. The database is a predefined databasewith the automatic number identification (ANI) providing the key. TheANI is used to identify the Directory Number (DN) of a callingsubscriber, thus the ANI is used to obtain the data associated with thecall.

Currently, the process is not performed efficiently. Several methods areused to provide the data to the other parties. For example, a trunkbasis is used wherein the trunk that the call came in on is identified.For those skilled in the art, a trunk group is sent and it is identifiedas being on Channel 2. Computer telephony integration (CTI) informationis exchanged between servers and communication nodes by means of CTImessages. For example, the CTI message may be used to identify thechannel the truck number was on. Thus, this information allows the dataand the call to be integrated. However, this method is very dependent onsynchronization of both the trunks and the CTI messages so that thechannel mapping enables integration of the data and the call.Nevertheless, the channel mapping would break down depending on volume.When time division multiplexing (TDM) was used, this method wasacceptable because hard coded channels were used. When the switch tovoice occurred, an algorithm was used to integrate the channel and thevoice. However, the expected destination channel did not necessarilycarry through to the other end as voice did not rely on a real cableextended from one place to another, but was implemented using datapackets.

Accordingly, there is a need for assigning to a call a unique keyassociated with caller specific data for database retrieval.

SUMMARY OF THE INVENTION

To overcome the limitations described above, and to overcome otherlimitations that will become apparent upon reading and understanding thepresent specification, embodiments for providing a Rolling ANIapplication that allows specific customer data to be written to arepository with a unique key for later retrieval is disclosed.

A Rolling ANI system allows customer data to be written to a databasewith a unique key so that when a customer call is transferred to anothermarket, or an outsource vendor, the specific customer data may be pulledwith the call transfer for the agentto see. The key is delivered withthe voice call via the CLI field, thus the agent system, i.e., vendor,at the far end knows where to go to immediately retrieve the data recordassociated with that specific customer's call. The Rolling ANI systemaccepts data from an ACD, or other CTI application, sets the Key thatwill be delivered with the voice call to its destination by overridingthe PSTN CLI field. The RollingANI system may normalize the input dataso that Line of Business (LOB) information may be sent back to the CCTto ensure proper routing.

A method for providing caller specific information with a call using akey for database retrieval of caller specific data is disclosed. Themethod includes maintaining a pool of rolling Automatic NumberIdentification (ANI) codes at a rolling ANI device, sending a call tothe rolling ANI device, assigning a rolling ANI to the call, providingthe assigned rolling ANI in a field identifying the call and routing thecall and the assigned rolling ANI in the field identifying the call to acall handler.

In another embodiment, a method for processing a call using callerspecific information is disclosed. The method includes receiving a voicepath and data associated with a call, parsing the data to determine arolling ANI associated with the call, obtaining caller specificinformation from a database record in a database identified by therolling ANI and using the obtained caller specific information toprocess the call seamlessly without prompting the caller for informationin the database record associated with the rolling ANI.

In another embodiment, another method for processing a call using callerspecific information is disclosed. The method includes maintaining apool of rolling Automatic Number Identification (ANI) codes at a rollingANI device, sending a call to the rolling ANI device, assigning arolling ANI to the call, providing the assigned rolling ANI in a fieldidentifying the call, routing the call and the assigned rolling ANI inthe field identifying the call to a call handler, receiving a voice pathand data associated with the call at the call handler, parsing the datato determine a rolling ANI associated with the call, obtaining callerspecific information from a database record in a database identified bythe rolling ANI and using the obtained caller specific information toprocess the call seamlessly without prompting the caller for informationin the database record associated with the rolling ANI.

In another embodiment, a system for enabling call processing usingcaller specific information is disclosed. The system includes anautomatic call distributor that includes automatic call distributormemory for storing data and an automatic call distributor processor,coupled to the automatic call distributor memory, the processormaintaining a pool of rolling Automatic Number Identification (ANI)codes in the memory, receiving a call, obtaining caller specificinformation from the caller associated with the call, assigning to thecall a rolling ANI from the pool of rolling ANI codes, storing theobtained caller specific information in a database record identified bythe assigned rolling ANI, providing the assigned rolling ANI in a fieldidentifying the call and routing the call and the assigned rolling ANIin the field identifying the call to a call handler and a computertelephony integration server, coupled to the automatic call distributor,for handling calls forwarded by the automatic call distributor, thecomputer telephony integration server including computer telephonyintegration server memory for storing retrieved data and a computertelephony integration server processor, coupled to the computertelephony integration server memory, for receiving a voice path and dataassociated with the call, parsing the data to determine a rolling ANIassociated with the call, obtaining caller specific information from adatabase record in a database identified by the rolling ANI and usingthe obtained caller specific information to process the call seamlesslywithout prompting the caller for information in the database recordassociated with the rolling ANI.

In another embodiment, an automatic call distributor system for enablingcall processing using caller specific information is disclosed. Theautomatic call distributor system includes automatic call distributormemory for storing data and an automatic call distributor processor,coupled to the automatic call distributor memory, the processormaintaining a pool of rolling Automatic Number Identification (ANI)codes in the memory, receiving a call, obtaining caller specificinformation from the caller associated with the call, assigning to thecall a rolling ANI from the pool of rolling ANI codes, storing theobtained caller specific information in a database record identified bythe assigned rolling ANI, providing the assigned rolling ANI in a fieldidentifying the call and routing the call and the assigned rolling ANIin the field identifying the call to a call handler.

In another embodiment, a computer telephony integration server forhandling calls is disclosed. The computer telephony integration serverincludes computer telephony integration server memory for storingretrieved data and a computer telephony integration server processor,coupled to the computer telephony integration server memory, forreceiving a voice path and data associated with a call, parsing the datato determine a rolling ANI associated with the call, obtaining callerspecific information from a database record in a database identified bythe rolling ANI and using the obtained caller specific information toprocess the call seamlessly without prompting the caller for informationin the database record associated with the rolling ANI.

In another embodiment, a computer-readable storage medium that includesinstructions, for providing caller specific information with a callusing a key for database retrieval of caller specific data is disclosed.The instructions include maintaining a pool of rolling Automatic NumberIdentification (ANI) codes at a rolling ANI device, sending a call tothe rolling ANI device, assigning a rolling ANI to the call, providingthe assigned rolling ANI in a field identifying the call, routing thecall and the assigned rolling ANI in the field identifying the call to acall handler, receiving a voice path and data associated with the callat the call handler, parsing the data to determine a rolling ANIassociated with the call, obtaining caller specific information from adatabase record in a database identified by the rolling ANI and usingthe obtained caller specific information to process the call seamlesslywithout prompting the caller for information in the database recordassociated with the rolling ANI.

These and various other advantages and features of novelty are pointedout with particularity in the claims annexed hereto and form a parthereof. However, for a better understanding of the disclosedembodiments, the advantages, and the objects obtained, reference shouldbe made to the drawings which form a further part hereof, and toaccompanying descriptive matter, in which there are illustrated anddescribed specific examples of the disclosed embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers representcorresponding parts throughout:

FIG. 1 illustrates a custom telephony routing system environment thatsupports a Rolling ANI system according to one embodiment;

FIG. 2 is a sequence chart that provides an overview of the call flowfor the Rolling ANI application according to one embodiment,

FIG. 3 provides a flowchart of the Rolling ANI eFlow according to anembodiment;

FIG. 4 is a block diagram illustrating example physical components of acomputing device and system architecture for providing Rolling ANI; and

FIGS. 5A and 5B illustrate a suitable mobile computing environment, forexample, a mobile computing device, a smart phone, a tablet personalcomputer, a laptop computer, and the like, with which embodiments may bepracticed.

DETAILED DESCRIPTION

Embodiments of the present invention are directed to a contact centercomputer telephony integration (CTI) system, herein referred to as theRolling ANI system, which allows a call to be assigned to a particularautomatic number identification (ANI) based on a value that is passed tothe system. The purpose of integrating a call to a specific ANI is touse this ANI as a key via the calling line identification (CLID)override capabilities of the automatic call distributor (ACD) whendelivering a call off premise.

The Rolling ANI is delivered in the CLID of the Integrated ServicesDigital Network (ISDN) message set and can be retrieved at the receivingsite to leverage a database call to integrate the customer/callerspecific data path to the voice path. This application may allow thecall center to create a pool of Rolling ANIs on the ACD and iterativelystep through each ANI and assign a call as necessary. This ensures thateach call will have a unique key associated with the caller-specificdata.

FIG. 1 illustrates a custom telephony routing system environment 100that supports a Rolling ANI system according to one embodiment. Asillustrated, the environment 100 may include caller terminals 115,180-A, and 180-B, a network 120, an automatic call distribution (ACD)server 130, a computer telephony integration (CTI) server 140, and aRolling ANI application engine 150 (also referred to herein as an eFlowapplication or system). It may be noted that in other implementations,environment 100 may include fewer, additional or different devices thanthose illustrated in FIG. 1.

Each of terminals 115, 180-A and 180-B may include a user device havingcommunication capability such as a telephone, cell phone, a mobilecomputing device (for example a smart phone), a computer, etc. Terminal115 may be operated by a caller 110 (e.g., a customer) and terminals180-A and 180-B may be operated by a call center agent 185. Network 120may include any type of network, such as a wide area network, a localarea network, a telephone network (i.e. a public switched telephonenetwork (PSTN) or a wireless network), the Internet, a private network,or a combination of networks, etc. Those skilled in the art recognizethe Network 120 may include at least one device to handle a call fromterminals.

The ACD server 130 may include a device that distributes incoming callsto one or more terminals 180-A, or agents 185. The ACD server may managecalls, queues, agent groups, caller service requests. It may alsoprovide for computer calls from the Web, email, fax, etc. The IVR 135provides caller service support through an interactive voice menusystem. For example, the caller 110 may indicate a response to a voiceprompt using a telephone dial pad or open dialog spoken by the caller.The CTI 140 server may include a device that provides an interactionbetween caller 110 contact channels and a computational device, such asa computer 180-B. Thus, the CTI server 140 may provide call-relatedinformation to a terminal 180-B for visual display. CTI server 140 mayroute a call to its proper extension and/or poll one or more back-enddatabases to relay call information to the appropriate terminal 180-B.

The Rolling ANI Application Engine 150 be located on a call data serverand may include a device that manages the data and one or more databases160. In one implementation, the call data may be managed (i.e. stored,retrieved, and processed) based on a unique key. The Rolling ANIapplication engine 150, sometimes referred to herein as eFlow, writesthe key and eight pieces of data to the database or repository 160. Thedatabase is provided for the vendor 187 to lookup the data associatedwith a call according to the key. Trunk lines provide the transmissionchannel between two points, for example, the customer 110 and the agent185 servicing the customer call. Accordingly, a call is received and thecustomer/caller 110 is validated by the system. All the informationabout the customer 110 is gathered. The call is provided to the RollingANI application server 150. Calls are counted by the Rolling ANIapplication and roll between 1 and a predetermined number, M. Forexample, if M is 10, the system count calls from 1 to 10 and resets thecounter repeatedly providing a rolling pool of ANIs to be used as callscome in. Those skilled in the art recognize that embodiments are notmeant to be limited to a repeating call count, but that a hard ANI maybe used. All of the data associated with a call is written to a database160 with the unique key being tied to the assigned rolling ANI.

Multiple lines of business may be outsourced to the vendor 187 for callhandling. Thus, it is important that the vendor 187 knows the call towhich the data is associated and the line of business where the vendor187 needs to route the call. The ANI is overwritten with this key oncethe call is delivered. The voice path routes 165 to the intendeddestination. The vendor 187 has the unique key and thus knowsimmediately to look up the associated data record in the database 160.The vendor 187 is therefore able to integrate the voice 165 and the data170 to handle the call seamlessly without having to prompt the customer110 for additional information, thereby preventing additional time beingwasted. The integration of the voice path and the data associated withthe call occurs quickly so by the time the count rolls over to the samecount again, the data in the database associated with the first call isno longer needed.

Accordingly, the Rolling ANI application is the custom telephony routingsystem that receives a value returned from the call count applicationand maps the received value to a predefined ANI in the Rolling ANI poolcreated on the ACD. To invoke this eFlow via the ACD, a ROLLINGANIsubtype can be issued from the local call control table (CCT). TheRolling ANI application will set the proper Line of Business (LOB) forthe call, map the proper Rolling ANI Key, write the Key and eight piecesof pertinent data to the Repository, and return the Rolling ANI Key inVariable A. The CCT can then dial out the call to the vendor 187 on thespecific Market/LOB and the Key will subsequently be delivered in theCLID field of the ISDN message set for their use.

FIG. 2 is a sequence chart 200 that provides an overview of the callflow for the Rolling ANI application according to one embodiment. TheeFlow 150, CTI 140 and Database 160 are shown together on the samemachine. However, those skilled in the art recognize that embodimentsmay provide these elements separately. There are 2 types of CCT(s) usedfor calling the Rolling ANI application: (1) the CCT that invokes theApplication and (2) the CCTs that the call is redirected to as a resultof the application selecting a Rolling ANI. To first call theapplication a CCT must invoke a Route Request to the eFlow 150 system.This value set in the SUBTYPE is a defined as ROLLINGANI. The CCT willissue a computer telephony integration module (CTIM) message using theSendTrackData step over a data interlink to the call managementinformation (CMI) server with a subtype of “ROLLINGANI” 215. The CMIserver will match the subtype to a routing device and forward therequest to the subsystem where the eFlow system 150 will process therequest 225 and return the call flow to the specific CCT 250. Thus, theACD 210 may send a CTI message 215 over to the CTI server 140, whichthen sends the data received 225 to the eFlow engine 150. The eFlowengine 150 manipulates the data by using the obtained customer data. Themessage not only includes the Key, but also includes the customer datathat the ACD 130 has gathered over the course of the call. This data 235is written to the database 160. Thus, eFlow writes the Key and eightpieces of data to repository 160.

The key is the RollingANI that was assigned to the call. For example, inthe case of Pensacola, Fla., the RollingANI starts at one 7-digit number1350001. The iterative process is managed by a Call Counter application.A key is incremented by 1000, 2000, 3000, etc. so that number in thatposition will represent the line of business, for example, Ser. No.13/510,002. The first three digits is the site ID and the fourth digitrepresents the line of business. Thus, the fourth digit is a 1, so theline of business may be Data Tech. This may be mapped to an internalline of business code. For example, DataTech represented by the 1 as thefourth digit is actually mapped to an internal line of business code7500004.

The CCT that the call is redirected to as a result of the Rolling ANIapplication 150 processing the call is part of a predefined set of CCTs.To ensure each CCT entry will have a one-to-one relationship with an ACDApplication, a common index number is assigned to each record within thetable, for example 2401 is assigned to both CCT and Application. EachApplication is mapped to a specific Rolling ANI hardcoded into the CLIDfield of that application. The 7 digit Rolling ANI/Key may be composedof the location code in the first three digits and the common index. Forexample, 135 may refer to Pensacola, Fla. This serves to create a poolof ANIs to ‘roll’ through and integrate to a call for later use in adatabase call.

The following table shows mapping of Rolling ANIs to a CCT and toApplications. As shown the CCT and Application are the same. The RollingANI/Key has the same common index as shown by the last digits.

CCT Application Rolling ANI/Key 2401 2401 1350001 2402 2402 1350002 24032403 1350003 2404 2404 1350004 2405 2405 1350005 2406 2406 1350006 24072407 1350007 2408 2408 1350008 2409 2409 1350009 2410 2410 1350010

FIG. 3 provides a flowchart 300 of the Rolling ANI eFlow according to anembodiment. The call flow has been handed off to the CTI server andRollingANI code has been invoked. As shown in FIG. 3, the process allowscustomer data to be written to a database with a unique key so that whena Customer call is transferred to another market, or an outsourcevendor, the specific customer data may be retrieved with the calltransfer for the agent to see. The key is delivered with the voice callvia the CLI field so the agent knows where that specific customer call'sdata record can be immediately retrieved. Start (305) begins the process300 and may provide initial error trapping. Error trapping may be splitinto three categories: CTI errors, database errors, and expressionerrors. CCT variables associated with the original track number (310)are retrieved and passed into the eFlow. Hard coded parameters arepassed into the eFlow engine 150 such as the customer account number,the track number, and other specific data and stored in variables (320).Variables may need to be validated (330) so the eFlow contains the logicto validate specific variables. For example, Variable A may need to bein the proper format required to return the Rolling ANI Key in theproper positions. Therefore, if the Rolling ANI Key needs to be returnedin positions 11-17 of Variable A, this may be accomplished by firstchecking the length of Variable A. If the length of variable A is lessthan a predetermined number Y, e.g., 10, the eFlow may need to padVariable A with as many Os as necessary to ensure the first Y positionsare populated so a later concatenation of the Rolling ANI Key will be inthe proper ordinance. This may be accomplished by a simple loop thatpads a “0” and then checks the length again.

The Set Key and Return CCT step (340) of the eFlow contains the corelogic used to create the Rolling ANI Key and return the call flow to theproper CCT/system combination that will result in the outbound calloverriding the CLID field with the Key. The index value may be stored ina variable, Variable C, which was passed in from the Call Countapplication (a CTI application leveraged to iteratively step through theRolling ANI pool). This value represents the Index for the Rolling ANIto be selected. It may accomplish this by adding the Index value to thepredetermined Rolling ANI Key and adding the Index value to 2400 forexample (see table above).

The Rolling ANI Key includes:

-   -   <Site ID∥nnnn>, where nnnn represents the current Nth call

Set LOB Code step (350) of the eFlow sets Variable C to the value of theLOB Code. This was preset in the calling CCT and was overwritten by CallCount application. To compensate for this, in the CCT all 7 digits inVariable C are used and the SITEID concatenated with 0000 is added tothe Index Value. Then x000 is added where x represents the code for aline of business. For example, if Data Tech is 1, 1000 is added, or 2000is added for another LOB such as Video Tech. This makes the 4^(th)position of variable C the indicator for LOB. Again, those skilled inthe art recognize that embodiments are not meant to be limited to aparticular number of digits. The particular number of digits or positionmay be altered without departing from the scope of the embodimentsdescribed herein.

Thus, the CTI Variable C from the CCT will contain:

-   -   (<Site ID∥nnnn>+x000 or x000), where nnnn represents the current        Nth call and x is the LOB code

Accordingly, the key is the RollingANI that was assigned to the call.For example, in the case of Pensacola, Fla., the RollingANI starts atone 7-digit number 1350001 as shown above. The iterative process ismanaged by Call Count application. A key is incremented by 1000, 2000,3000, etc. so that number in that position will represent the line ofbusiness, e.g., 13510002. The first three digits is the site ID and thefourth digit represents the line of business. Thus, the fourth digit isa 1, so the line of business is DataTech. This may be mapped to aninternal line of business code. For example, DataTech represented by the1 as the fourth digit is actually mapped to an internal line of businesscode such as 7500004.

The first variable (variable A) is set back to the original value passedin concatenated with the Rolling ANI Key (360). The remaining Variables(variables B, D, E) are also set back to the original values to bepassed back to CCT (370).

The Write to Repository step (380) of the eFlow process writes the 8pertinent caller specific data fields and key to the local Repositoryfor retrieval at a later time. The data fields are as follows:

-   -   Key is a Rolling ANI for integrating voice path and data    -   Track Number is the Track Number used for escalation notes    -   Call ID is the Call ID used for building CTI transfer back        messages    -   Variable A is the original variable A concatenated with the        Rolling ANI Key    -   Variable B is the customer account number for database calls    -   Variable c is the LOB Code for identification and screen pops (a        screen pop is a window or dialog box that autonomously appears        on the desktop, displaying information for a call simultaneously        sent to that agent's telephone)    -   Variable D is the Site ID and last 4 of original DNIS for ICOMs        calls    -   Variable E is other customer data        The application engine (eFlow) 150 may return control of the        call to the proper CCT as determined by the application (390).

FIG. 4 illustrates an example computing device 400 with whichembodiments of the present invention may be implemented. In someembodiments, the CTI server 140, the Rolling ANI Application Engine 150,and/or the Database 160 may be implemented using one or more computingdevices like the computing device 400. It should be appreciated that inother embodiments, the CTI server 140, the Rolling ANI ApplicationEngine 150, and/or the Database 160 may be implemented using computingdevices having hardware components other than those illustrated in theexample of FIG. 4.

Computing devices may be implemented in different ways in differentembodiments. For instance, in the example of FIG. 4, the computingdevice includes a processing system 404, memory 402, a network interface406, a secondary storage device 408, an input device 410, a videointerface 412, a display unit 414, and a communication medium 416. Inother embodiments, the computing device 400 may be implemented usingmore or fewer hardware components (e.g., a video interface, a displayunit, or an input device) or in combination with other types of computersystems and program modules.

The memory 402 includes one or more computer-readable storage mediacapable of storing data and/or computer-executable instructions. Memory402 thus may store the computer-executable instructions that, whenexecuted by processor 404, cause the Rolling ANI application engine 150to assign a unique key to customer data as described above withreference to FIGS. 1-3 and store customer specific data to database 160.

In various embodiments, the memory 402 is implemented in various ways.For example, the memory 402 can be implemented as various types ofcomputer-readable storage media. Example types of computer-readablestorage media include, but are not limited to, solid state memory, flashmemory, dynamic random access memory (DRAM), double data ratesynchronous dynamic random access memory (DDR SDRAM), DDR2 SDRAM, DDR3SDRAM, read-only memory (ROM), reduced latency DRAM,electrically-erasable programmable ROM (EEPROM), and other types ofdevices and/or articles of manufacture that store data.

According to embodiments, the term computer-readable media includescommunication media and computer-readable storage media. Communicationmedia include information delivery media. Computer-executableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, may be embodied on a communications medium. The termmodulated data signal describes a signal that has one or morecharacteristics set or changed in such a manner as to encode informationin the signal. For example, communication media can include wired media,such as a wired network or direct-wired connection, and wireless media,such as acoustic, radio frequency (RF), infrared, and other wirelessmedia.

The term computer-readable storage medium may also refer to devices orarticles of manufacture that store data and/or computer-executableinstructions readable by a computing device. The term computer-readablestorage media encompasses volatile and nonvolatile, removable andnon-removable media implemented in various methods or technologies forstorage and retrieval of information. Such information can include datastructures, program modules, computer-executable instructions, or otherdata.

The processing system 404 includes one or more processing units, whichmay include tangible integrated circuits that selectively executecomputer-executable instructions. In various embodiments, the processingunits in the processing system 404 are implemented in various ways. Forexample, the processing units in the processing system 404 can beimplemented as one or more processing cores. In this example, theprocessing system 404 can comprise one or more Intel Coremicroprocessors. In another example, the processing system 404 cancomprise one or more separate microprocessors. In yet another exampleembodiment, the processing system 404 can comprise Application-SpecificIntegrated Circuits (ASICs) that provide specific functionality. In yetanother example, the processing system 404 provides specificfunctionality by using an ASIC and by executing computer-executableinstructions.

The computing device 400 may be enabled to send data to and receive datafrom a communication network via a network interface card 406. Indifferent embodiments, the network interface card 306 is implemented indifferent ways, such as an Ethernet interface, a token-ring networkinterface, a fiber optic network interface, a wireless network interface(e.g., Wi-Fi, Wi-Max, etc.), or another type of network interface. Thenetwork interface may allow the device to communicate with otherdevices, such as over a wireless network in a distributed computingenvironment, a satellite link, a cellular link, and comparablemechanisms. Other devices may include computer device(s) that executecommunication applications, storage servers, and comparable devices.

The secondary storage device 408 includes one or more computer-readablestorage media, and may store data and computer-executable instructionsnot directly accessible by the processing system 404. That is, theprocessing system 404 performs an I/O operation to retrieve data and/orcomputer-executable instructions from the secondary storage device 408.In various embodiments, the secondary storage device 408 can beimplemented as various types of computer-readable storage media, such asby one or more magnetic disks, magnetic tape drives, CD-ROM discs,DVD-ROM discs, BLU-RAY discs, solid state memory devices, and/or othertypes of computer-readable storage media.

The input device 410 enables the computing device 400 to receive inputfrom a user. Example types of input devices include, but are not limitedto, keyboards, mice, trackballs, stylus input devices, key pads,microphones, joysticks, touch-sensitive display screens, and other typesof devices that provide user input to the computing device 400.

The video interface 412 outputs video information to the display unit414. In different embodiments, the video interface 412 is implemented indifferent ways. For example, the video interface 412 is a videoexpansion card. In another example, the video interface 412 isintegrated into a motherboard of the computing device 400. In variousembodiments, the display unit 414 can be a an LCD display panel, atouch-sensitive display panel, an LED screen, a projector, a cathode-raytube display, or another type of display unit. In various embodiments,the video interface 412 communicates with the display unit 414 invarious ways. For example, the video interface 412 can communicate withthe display unit 414 via a Universal Serial Bus (USB) connector, a VGAconnector, a digital visual interface (DVI) connector, an S-Videoconnector, a High-Definition Multimedia Interface (HDMI) interface, aDisplayPort connector, or another type of connection.

The communications medium 416 facilitates communication among thehardware components of the computing device 400. In differentembodiments, the communications medium 416 facilitates communicationamong different components of the computing device 400. For instance, inthe example of FIG. 4, the communications medium 416 facilitatescommunication among the memory 402, the processing system 404, thenetwork interface card 406, the secondary storage device 408, the inputdevice 410, and the video interface 412. In different embodiments, thecommunications medium 416 is implemented in different ways, such as aPCI bus, a PCI Express bus, an accelerated graphics port (AGP) bus, anInfiniband interconnect, a serial Advanced Technology Attachment (ATA)interconnect, a parallel ATA interconnect, a Fiber Channel interconnect,a USB bus, a Small Computing system Interface (SCSI) interface, oranother type of communications medium.

The memory 402 stores various types of data and/or softwareinstructions. For instance, in the example of FIG. 4, the memory 402stores a Basic Input/Output System (BIOS) 418, and an operating system420. The BIOS 418 includes a set of software instructions that, whenexecuted by the processing system 404, cause the computing device 400 toboot up. The operating system 420 includes a set of softwareinstructions that, when executed by the processing system 404, cause thecomputing device 400 to provide an operating system that coordinates theactivities and sharing of resources of the computing device 400. Thememory 402 also stores one or more application programs 422 that, whenexecuted by the processing system 404, cause the computing device 400 toprovide applications to users. According to an embodiment, memory 402may store a rolling ANI application engine 150. The memory 402 alsostores one or more utility programs 424 that, when executed by theprocessing system 404, cause the computing device 400 to provideutilities to other software programs.

Embodiments of the present invention may be utilized in variousdistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network in adistributed computing environment.

Moreover, embodiments may be implemented such that each or many of thecomponents illustrated in FIG. 4 may be integrated onto a singleintegrated circuit. When operating via such a single integrated circuit,the functionality, described herein, with respect to the rolling ANIapplication engine 150 may be operated via application-specific logicintegrated with other components of the computing device/system 400 onthe single integrated circuit.

FIG. 4 illustrates a system architecture 400 for providing a rolling ANIapplication that assigns a unique key associated with the callerspecific data to each call for database retrieval, as described above.Calls made by a calling party, interacted with or edited in associationwith a rolling ANI application engine 150 may be stored in differentcommunication channels or other storage types. The rolling ANIapplication engine 150 may use any of different communication channelsor other storage types or the like for enabling data utilization, asdescribed herein. A server 140 may provide the ANI key to clients. Asone example, a server may be a web server providing the rolling ANIapplication engine 150 over the web. Server 140 may provide the ANI keyover the web to clients through a network 120. Examples of clients thatmay obtain the caller-specific information include computing device 450,which may include any general purpose personal computer (such ascomputing device 400), a tablet computing device 470 and/or mobilecomputing device 460, such as smart phones.

FIGS. 5A and 5B are block diagrams of a mobile computing device withwhich embodiments of the present invention may be practiced. The mobilecomputing device 500 is illustrative of any suitable device, such as amobile telephone, personal digital assistant (PDA), or handheldcomputer, operative to send, receive and process wireless communicationsaccording to embodiments of the present invention. A display screen 505is operative for displaying a variety of information such as informationabout incoming and outgoing communications, as well as, a variety ofdata and displayable objects, for example, text, alphanumeric data,photographs, and the like.

Data input to the device 500 may be performed via a variety of suitablemeans, such as, touch screen input via the display screen 505, keyboardor keypad input via a data entry area 510, key input via one or moreselectable buttons or controls 515, voice input via a microphone 520disposed on the device 500, photographic input via a camera 525functionality associated with the mobile computing device, or any othersuitable input means. Data may be output via the device 500 via anysuitable output means, including but not limited to, display on thedisplay screen 505, audible output via an associated speaker 530 orconnected earphone system, vibration module for providing tactileoutput, and the like.

Referring now to FIG. 5B, operational unit 535 is illustrative ofinternal operating functionality of the mobile computing device 500. Aprocessor 540 is illustrative of a general purpose computer processorfor processing incoming and outgoing data and communications andcontrolling operation of the device and associated software applicationsvia a mobile computing device operating system. Memory 545 may beutilized for storing a device operating system, device programming, oneor more stored applications, for example, mobile telephone applications,data processing applications, calculators, games, Internet browsingapplications, navigation applications, acceleration applications, cameraand/or video applications, etc. Other applications may be loaded intomemory 562 and run on the mobile computing device 502, including therolling ANI application engine 150, described herein.

Mobile computing device 500 may contain an accelerometer 555 fordetecting acceleration, and can be used to sense orientation, vibration,and/or shock. Mobile computing device 500 may contain a globalpositioning system (GPS) system (e.g., GPS send/receive functionality)560. A GPS system 560 uses radio waves to communicate with satellitesorbiting the Earth. Some GPS-enabled mobile computing devices usewireless-assisted GPS to determine a user's location, wherein the deviceuses orbiting GPS satellites in conjunction with information about thedevice's mobile phone signal. Radio functions 550 include all requiredfunctionality, including onboard antennae, for allowing the device 500to communicate with other communication devices and systems via awireless network. Radio functions 550 may be utilized to communicatewith a wireless or WIFI-based positioning system to determine a device's500 location.

Although described herein in combination with mobile computing device500, in alternative embodiments the invention may be used in combinationwith any number of computer systems, such as in desktop environments,laptop or notebook computer systems, multiprocessor systems,micro-processor based or programmable consumer electronics, networkedPCs, mini computers, main frame computers and the like. Embodiments ofthe present invention may be utilized in various distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network in a distributed computingenvironment, and where programs may be located in both local and remotememory storage.

Embodiments, for example, are described above with reference to blockdiagrams and/or operational illustrations of methods, systems, andcomputer program products according to embodiments. The functions/actsnoted in the blocks may occur out of the order as shown in any flowchartor described herein with reference to FIGS. 1-5. For example, twoprocesses shown or described in succession may in fact be executedsubstantially concurrently or the blocks may sometimes be executed inthe reverse order, depending upon the functionality/acts involved.

The foregoing description of the exemplary embodiment of the inventionhas been presented for the purposes of illustration and description. Itis not intended to be exhaustive or to limit the invention to theprecise form disclosed. Many modifications and variations are possiblein light of the above teaching. It is intended that the scope of theinvention be limited not with this detailed description, but rather bythe claims appended hereto.

What is claimed is:
 1. A system for enabling call processing usingcaller specific information, comprising: an automatic call distributorcomprising: automatic call distributor memory for storing data; and aautomatic call distributor processor, coupled to the automatic calldistributor memory, the processor maintaining a pool of rollingAutomatic Number Identification (ANI) codes in the memory, receiving acall, obtaining caller specific information from the caller associatedwith the call, assigning to the call a rolling ANI from the pool ofrolling ANI codes, storing the obtained caller specific information in adatabase record identified by the assigned rolling ANI, providing theassigned rolling ANI in a field identifying the call and routing thecall and the assigned rolling ANI in the field identifying the call to acall handler; and a computer telephony integration server, coupled tothe automatic call distributor, for handling calls forwarded by theautomatic call distributor, the computer telephony integration servercomprising: computer telephony integration server memory for storingretrieved data; and a computer telephony integration server processor,coupled to the computer telephony integration server memory, forreceiving a voice path and data associated with the call, parsing thedata to determine a rolling ANI associated with the call, obtainingcaller specific information from a database record in a databaseidentified by the rolling ANI and using the obtained caller specificinformation to process the call seamlessly without prompting the callerfor information in the database record associated with the rolling ANI.2. The system of claim 1, wherein the automatic call distributorprocessor initially receives the call, validates a caller associatedwith the call, obtains caller specific information from the callerassociated with the call and stores the obtained caller specificinformation in a database record identified by the assigned rolling ANI.3. The system of claim 1, wherein the automatic call distributorprocessor routes the call and the assigned rolling ANI in the fieldidentifying the call to a call handler by routing the call to thecomputer telephony integration server for managing interaction with thecaller using information from a database record identified by therolling ANI.
 4. The system of claim 1, wherein the automatic calldistributor processor assigns a rolling ANI to the call that includesidentification of a line of business associated with the call andidentification of a geographic area associated with the caller.
 5. Thesystem of claim 1, wherein the automatic call distributor processorprovides a counter to provide a cyclic maximum count used to cyclethrough the pool of rolling ANI codes.
 6. The system of claim 1, whereinthe automatic call distributor processor provides a hard coded ANI fromthe pool of rolling ANI codes.
 7. The system of claim 1, wherein theautomatic call distributor processor provides the assigned rolling ANIin a calling line identification field and stores in a database acustomer account number, a customer site identifier for the customer,information about a service level for the customer, a type of serviceavailable in the customer site and a service currently associated withthe caller.
 8. An automatic call distributor system for enabling callprocessing using caller specific information, comprising: automatic calldistributor memory for storing data; and an automatic call distributorprocessor, coupled to the automatic call distributor memory, theprocessor maintaining a pool of rolling Automatic Number Identification(ANI) codes in the memory, receiving a call, obtaining caller specificinformation from the caller associated with the call, assigning to thecall a rolling ANI from the pool of rolling ANI codes, storing theobtained caller specific information in a database record identified bythe assigned rolling ANI, providing the assigned rolling ANI in a fieldidentifying the call and routing the call and the assigned rolling ANIin the field identifying the call to a call handler.
 9. The automaticcall distributor system of claim 8, wherein the rolling ANI is assignedto the call in a calling line identification field and includesidentification of a line of business associated with the call andidentification of a geographic area associated with the caller.
 10. Acomputer telephony integration server for handling calls, comprising:computer telephony integration server memory for storing retrieved data;and a computer telephony integration server processor, coupled to thecomputer telephony integration server memory, for receiving a voice pathand data associated with a call, parsing the data to determine a rollingANI associated with the call, obtaining caller specific information froma database record in a database identified by the rolling ANI and usingthe obtained caller specific information to process the call seamlesslywithout prompting the caller for information in the database recordassociated with the rolling ANI.
 11. The computer telephony integrationserver of claim 10, wherein the rolling ANI is further parsed toidentify a line of business associated with the call and a geographicarea associated with the caller.